home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
ssrun.z
/
ssrun
Wrap
Text File
|
1998-10-30
|
7KB
|
198 lines
SSSSSSSSRRRRUUUUNNNN((((1111)))) SSSSSSSSRRRRUUUUNNNN((((1111))))
NNNNAAAAMMMMEEEE
ssrun - set up and run a process to collect SpeedShop performance data
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
ssssssssrrrruuuunnnn [options] command [args]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
_s_s_r_u_n is used by the SpeedShop performance tools to establish the
environment to capture performance data for an executable, and create a
process from the executable (or an instrumented version), and then run
it. When performance data is collected, it is written to a file whose
name is of the form <command>.<exptype>.<code><pid> where <code> can be
'm' for the master process created by _s_s_r_u_n, 'p' for a process created by
a call to _s_p_r_o_c(), 'f' for a process created by a call to _f_o_r_k(), 'e' for
a process created by a call to _e_x_e_c(), 's' for a system call process and
'fe' for a process created by a call to _f_o_r_k() and _e_x_e_c() with
environment variable _SPEEDSHOP_TRACE_FORK_TO_EXEC being set to False.
Data may be examined using prof(1).
The following options may be given:
- <_e_x_p_t_y_p_e> | -_e_x_p <_e_x_p_t_y_p_e>
Specifies the type of SpeedShop experiment to run. The value of
<_e_x_p_t_y_p_e> specifies the particular performance data that will be
recorded during the run. See the speedshop(1) man page for the list
of supported experiments. Some experiments require that the target
process be instrumented to collect data; if necessary,
instrumentation (by pixie(1)) will be performed, and the resultant
instrumented executable run. The experiment type may also be set by
setting the environment variable _SPEEDSHOP_EXPERIMENT_TYPE. If
both are set, and they are different, a warning message will be
printed, and the command line argument will prevail.
Each experiment type corresponds to a set of "marching orders" that
the runtime will use. This facility is provided to allow users to
specify customized experiments, and will be more fully documented in
subsequent releases. Marching orders may also be set by setting the
environment variable _SPEEDSHOP_MARCHING_ORDERS, or by providing a
_m_o argument to ssssssssrrrruuuunnnn. If a known experiment is specified, and the
marching orders are also specified, and they are different, a
warning will be printed, and the marching orders will prevail. If
the experiment is not known, its name will be used and no warning
issued; if no experiment name was specified, the experiment name
will be set to "marching-orders".
-_m_o _m_a_r_c_h_i_n_g-_o_r_d_e_r_s
Specifies marching orders; if this option is used, the environment
variable _SPEEDSHOP_MARCHING_ORDERS will not be examined.
-_p_u_r_i_f_y
Specifies (if the independent Purify product is installed), that
purify should be run on the target, and the resulting purify'd
executable run. Note that -_p_u_r_i_f_y and SpeedShop performance
PPPPaaaaggggeeee 1111
SSSSSSSSRRRRUUUUNNNN((((1111)))) SSSSSSSSRRRRUUUUNNNN((((1111))))
experiments can not be combined.
-_v | -_v_e_r_b_o_s_e
Specifies that a log of the operation of _s_s_r_u_n should be printed to
stderr. The same behavior occurs if the environment variable
_SPEEDSHOP_VERBOSE is set a to a zero-length string.
-_V Specifies that a detailed log of the operation of _s_s_r_u_n should be
printed to stderr. The same behavior occurs if the environment
variable _SPEEDSHOP_VERBOSE is set a to a non-zero-length string.
In this case, a non-zero-length _SPEEDSHOP_VERBOSE environment
variable will be set, so that the target and any descendant
processes will see it.
-_w_o_r_k_s_h_o_p
Forces special instrumentation so that the experiment files can be
read by WorkShop's cvperf analyzer unless one of the capture modules
of the experiment also requires instrumentation.
-_q_u_i_e_t
Suppresses all output other than error messages. If set,
_SPEEDSHOP_SILENT will be set, so that the target and any descendant
processes will see it.
-_h_a_n_g
Specifies that the process should be left waiting just before
executing its first instruction.
-_p_o_r_t _h_o_s_t_n_a_m_e _p_o_r_t_n_o
Specifies that the process is to be left waiting, and, in addition,
notifications of status be sent to the socket on the host given by
_h_o_s_t_n_a_m_e and port given by _p_o_r_t_n_o from the command line. When the
process is ready, a message of the form "running <pid> <host>" will
be sent to inform the requestor of the target process' PID, and
(possibly remote) host. A debugger may then attach to it and take
control of its execution.
-_x Specifies that the process is to be left waiting, and, in addition,
that the window of the WorkShop Debugger requesting the creation (as
given by the _d_i_s_p_l_a_y-_i_d and _w_i_n_d_o_w-_i_d on the command line) be
informed of the target process' PID. A debugger may then attach to
it and take control of its execution.
-_n_a_m_e _t_a_r_g_e_t-_n_a_m_e
Specifies that the target, instrumented or not, should be run with
argv[0] set to _t_a_r_g_e_t-_n_a_m_e. Normally, both instrumented and
uninstrumented executables are run with argv[0] set to the original
name.
PPPPaaaaggggeeee 2222
SSSSSSSSRRRRUUUUNNNN((((1111)))) SSSSSSSSRRRRUUUUNNNN((((1111))))
SEE ALSO
speedshop(1), ssdump(1), prof(1), pixie(1), malloc_ss(3), fpe_ss(3),
io_ss(3), cvperf(1)
PPPPaaaaggggeeee 3333